feat: Adding unit tests for start - Covering goals, defaultCharacters, relationships, evaulators, posts, database, messages #367
+1,193
−7
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Relates to:
#64
#340
Risks:
low - Only tests are affected
Background:
Unit tests as a starter
What does this PR do?
Includes tests for core package
What kind of change is this?
Improvements/Features
Adding basic unit tests is a good starter for having good Testing/Quality Assurance process
Documentation changes needed?
Yes, but not in the main Documentation, README-TESTs.md is added for test documentation
Testing:
Running the tests and making sure they are valid.
Where should a reviewer start?
In packages/core
Detailed testing steps:
Navigating to packages/core folder, runing pnpm install, pnpm test to run tests